Open
Conversation
…s, instead require the apex name to be passed in. This fixes issues such as signing wrongly identifying an out-of-zone name (such as a glue that sorts earlier than the zone) as the apex instead of the zone itself. Also update Rust Doc strings to more closely match current behaviour of the signing APIs.
…ion, add some more NSEC logging, and adjust some logging levels.
BoomchainLabs
approved these changes
Jun 30, 2025
Contributor
|
@ximon18 do we want to keep this and fix the conflicts? |
Member
Author
|
The extra logging in principle benefits debugging of Cascade and IIRC these changes are included in the patches-for-nameshed-prototype branch. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
As already existed for NSEC generation. Also added some more logging in these functions and adjusted some logging levels.